home *** CD-ROM | disk | FTP | other *** search
/ NetNews Offline 2 / NetNews Offline Volume 2.iso / news / comp / lang / c++-part1 / 1038 < prev    next >
Encoding:
Internet Message Format  |  1996-08-06  |  1.5 KB
  1. Path: library.erc.clarkson.edu!rpi!not-for-mail
  2. From: floydb1@lib108.its.rpi.edu (Barry B Floyd)
  3. Newsgroups: comp.lang.c++
  4. Subject: Re: Are ostream.write and istream.read non-reciprocal??
  5. Date: 8 Jan 1996 14:51:37 -0500
  6. Organization: Rensselaer Polytechnic Institute, Troy, NY.
  7. Message-ID: <4crsk9$7u5@lib108.its.rpi.edu>
  8. References: <60ii536@kbrady.ultranet.com>
  9. NNTP-Posting-Host: lib108.its.rpi.edu
  10. X-newsreader: xrn 7.04-beta-11
  11.  
  12.  
  13. In article <60ii536@kbrady.ultranet.com>, Ken Brady <kbrady@ultranet.com> writes:
  14.  
  15. stuff deleted...
  16.  
  17. |> The stream seems to be  
  18. |> doing some sort of string-formatting even though I've specified it as  
  19. |> binary.
  20. |> 
  21. |> Are ostream.write and istream.read non-reciprocal??  How can I write a  
  22. |> simple array of arbitrarily-valued char without resorting to a slow  
  23. |> loop of put(p[i])??
  24. |> 
  25.  
  26. If you are doing this on a Unix system I believe there is in effect
  27. no "binary" for streams. I recall previous postings indicating that
  28. ios::binary primarily (only?) changes how CR-LF's are handled.
  29.  
  30. From you posting, this would seem to be the case ( i.e. 
  31. |> The stream seems to be  
  32. |> doing some sort of string-formatting even though I've specified it as
  33. |> binary.
  34. )
  35. -- 
  36. +--------------------------------------------------------------------+ 
  37. | Barry B. Floyd                   \\\               floydb1@rpi.edu |
  38. | RPI Alum. '84 '87 '88              \\\                             |
  39. +--------------------------------------------------------------------+
  40.